Adullah, Please let us know if this is going to cross site DAG or same site DAG. As you mentioned you have installed 4 roles in both the exchange server. When you put Witness file on domain controller you need to make sure that Exchange Trusted subsystem group is added to Administrators group. After failover to let the exchange server know to which server they should redirect the connection. You will have to run the command Get-Mailboxdatabase | Set-Mailboxdatabase -RPCClientaccessserver servername If both the DAG members are in the same site then the failover will happen automatically for Mailbox and HT roles however for CAS server you will have to run the above mentioned command. If both the DAG members are in different site then you will to follow below steps Make sure that DatacenterActivationMode=DagOnly Apply the following command on remote site on the server in power shell window Stop-databaseAvailabilityGroup Identity PSDAG1 ConfigurationOnly ActiveDirectorySite <Primary site name> Stop Cluster service on Remote site server using one of the following methods: a- Start menu Administrative tools Windows power shell write Stop-Service ClusSvc b- Start menu All programs Accessories open Command Prompt write net stop clussvc Apply the following command in mailbox power shell: Restore-databaseAvailabilityGroup Identity PSDAG1 ActiveDirectorySite <RemoteSite> Now the Database should move automatically to Remote Site mailbox server. Important NOTE: if the database did not move automatically we need to do it manually from the power shell with this command: Move-ActiveMailboxDatabase Move file share witness to other site DC (specific to your scenario ) Get-Mailboxdatabase | Set-Mailboxdatabase -RPCClientaccessserver servername Clients will then automatically connect to the new service endpoints in one of two ways: 1- Clients will continue to try to connect, and should automatically connect after the TTL has expired for the original DNS entry, and after the entry is expired from the client's DNS cache. Users can also run the ipconfig /flushdns command from a command prompt to manually clear their DNS cache. 2- Clients starting or restarting will perform a DNS lookup on startup and will get the new IP address for the service endpoint, which will be a Client Access server or array in the second datacenter. If the DNS records didnt change automatically we need to change it manually Change the host records a- Autodiscover to 192.168.1.55 <------> for example b- Owa to 192.168.1.55 c- RemoteSiteServer-CAS2 192.168.1.55 Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hasnain Shaikh| My blogs: http://messagingserversupport.com

dear friends : i have new setup that containe 1- domain (dc) 2- TMG 3- exchnage 1 4- exchange 4 i need the correct instullation and configuration steps i know is to mush information. i need the to configure failover cluster between 2 exchange server after that i want to do DAG for mail box and i need to do CAS for users (outlook) already i did the LAB in my server using Hyper V i installed the 4 roles in both exchange : CAS + MAILBOX+UNIFEED MESSAGE+HUB TRANSPORT then after i did the cluster steps i configure the DAG but i face problem here i put the Witness file in Active dirctory it must me the both exchange see the file only the exchange 1 is showing but when i click manage the DAG is showing the exchange 2 is there but the exchange 1 is not showing. even it must be after cluster the both exchnage 1 and 2 to be apper in database managment ( exchange 1 ---mounted ) exchange 2--helthy) now in my setup is does not show only exchnage 1 is showing now i have problem in CAS SERVER what configuration i have to do to implment the CAS between the two exchange server means the user outlook how they will connect to CAS and how the cluster fail over will work with the 2 exchange server if the exchange server 1 is down what i have to do to let the exchange server 2 to work or it will be up automatically i know is to much information but i know you will help with this thanks alot for your support

Adullah, Please let us know if this is going to cross site DAG or same site DAG. As you mentioned you have installed 4 roles in both the exchange server. When you put Witness file on domain controller you need to make sure that Exchange Trusted subsystem group is added to Administrators group. After failover to let the exchange server know to which server they should redirect the connection. You will have to run the command Get-Mailboxdatabase | Set-Mailboxdatabase -RPCClientaccessserver servername If both the DAG members are in the same site then the failover will happen automatically for Mailbox and HT roles however for CAS server you will have to run the above mentioned command. If both the DAG members are in different site then you will to follow below steps Make sure that DatacenterActivationMode=DagOnly Apply the following command on remote site on the server in power shell window Stop-databaseAvailabilityGroup Identity PSDAG1 ConfigurationOnly ActiveDirectorySite <Primary site name> Stop Cluster service on Remote site server using one of the following methods: a- Start menu Administrative tools Windows power shell write Stop-Service ClusSvc b- Start menu All programs Accessories open Command Prompt write net stop clussvc Apply the following command in mailbox power shell: Restore-databaseAvailabilityGroup Identity PSDAG1 ActiveDirectorySite <RemoteSite> Now the Database should move automatically to Remote Site mailbox server. Important NOTE: if the database did not move automatically we need to do it manually from the power shell with this command: Move-ActiveMailboxDatabase Move file share witness to other site DC (specific to your scenario ) Get-Mailboxdatabase | Set-Mailboxdatabase -RPCClientaccessserver servername Clients will then automatically connect to the new service endpoints in one of two ways: 1- Clients will continue to try to connect, and should automatically connect after the TTL has expired for the original DNS entry, and after the entry is expired from the client's DNS cache. Users can also run the ipconfig /flushdns command from a command prompt to manually clear their DNS cache. 2- Clients starting or restarting will perform a DNS lookup on startup and will get the new IP address for the service endpoint, which will be a Client Access server or array in the second datacenter. If the DNS records didnt change automatically we need to change it manually Change the host records a- Autodiscover to 192.168.1.55 <------> for example b- Owa to 192.168.1.55 c- RemoteSiteServer-CAS2 192.168.1.55 Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hasnain Shaikh| My blogs: http://messagingserversupport.com